Add Google Workspace connection documentation#36243
Merged
maddiefranke merged 9 commits intomasterfrom Apr 30, 2026
Merged
Conversation
Covers OAuth2 setup, scope selection, and connection creation in Datadog for Gmail, Calendar, Drive, Docs, Sheets, Forms, and Chat.
Contributor
Preview links (active after the
|
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
|
Added a Jira card for editorial review: DOCS-14163 |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Use the {{< ui >}}{{< /ui >}} shortcode for Datadog UI labels for consistency with other connection docs
- Renumber reference links sequentially (skipped [3] previously)
- Remove numerals from prerequisite subheadings to produce cleaner anchors
- Rephrase step 2 of "Enable the required APIs" so the table reads as part of the procedure
- Drop redundant "below" after in-page anchor links
- Replace "info" with "information" in the User identity scopes table
- Reword "Google Docs documents" and "Google Sheets spreadsheets" to remove noun stacking
estherk15
reviewed
Apr 29, 2026
Contributor
There was a problem hiding this comment.
Thanks @maddiefranke for adding this information! I left a few comments on the content. Also, created a separate PR for formatting fixes, if these look OK, you can merge to your branch: #36355
- Reword Prerequisites intro and replace inline Google Cloud project creation steps with a link to Google's own guide. - Link "app verification" to Google's restricted-scope verification doc and clarify "authorize" -> "authorize the app". - Combine the Authorized JavaScript origins and Authorized redirect URIs steps into a single instruction with a shared note. - Reword the Authorize URL/Token URL step to "Leave [...] as their pre-populated default values". - Renumber reference-style links in usage order and drop the now-unused Google Cloud Console root link. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
@estherk15 Thanks for the review :) I've merged your branch in and updated with your other suggestions - super helpful!! |
estherk15
approved these changes
Apr 30, 2026
Contributor
estherk15
left a comment
estherk15
left a comment
There was a problem hiding this comment.
Thanks for the updates and for your work on this!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds setup documentation for Google Workspace connections in Datadog Actions, covering OAuth2 client configuration in Google Cloud and connection creation in Datadog.
What does this PR do? What is the motivation?
Adds a new doc page at
/actions/connections/google_workspacethat walks users through:Also includes a full scopes reference table for Gmail, Calendar, Drive, Docs, Sheets, Forms, Chat, user identity, and Workspace Admin.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
AI assistance
Used Claude Code for drafting and editing.
Additional notes